-
-
Notifications
You must be signed in to change notification settings - Fork 4.7k
feat: optimize user mount cache #57815
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
I would expect the performance comparison to go the other way around for instances that have a few mounts per user but a lot of files. Adding both comparisons and hoping the DB knows what to do is probably for the best. |
|
On my instance, having both still filter on |
e8727f6 to
9560e1c
Compare
|
I was able to trigger the same EXPLAIN by adding a condition to the join: |
|
/backport to stable33 |
Signed-off-by: Benjamin Gaussorgues <benjamin.gaussorgues@nextcloud.com>
9560e1c to
f71f19c
Compare
|
/backport to stable33 |
|
The backport to # Switch to the target branch and update it
git checkout stable33
git pull origin stable33
# Create the new backport branch
git checkout -b backport/57815/stable33
# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick f71f19c0
# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/57815/stable33Error: Failed to create pull request: Validation Failed: {"resource":"PullRequest","code":"custom","message":"A pull request already exists for nextcloud:backport/57815/stable33."} - https://docs.github.com/rest/pulls/pulls#create-a-pull-request Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports. |
|
Not sure why it was auto-merged because it breaks sharding according to tests… |
Optimize requests like:
TODO
Explain
Before
After
The change allows to filter on filecache first
(Rough) Benchmark